How Do Software Architects Consider Non-Functional Requirements: A Survey
نویسندگان
چکیده
[Context and motivation] Non-functional requirements (NFRs) play a fundamental role when software architects need to make informed decisions. Criteria like efficiency or integrity determine up to a great extent the final form that the logical, development and deployment architectural views take. [Question/problem] Continuous evidence is needed about the current industrial practices of software architects concerning NFRs: how do they consider them, and what are the most influential types in their daily work. [Principal ideas/results] We ran a web survey addressed to software architects about these issues. We got 60 responses that give some light to the questions above. [Contribution] Some empirical data has been gathered from industry. The results of this survey may serve as input for researchers in order to decide in which types of NFRs may be necessary to invest more research effort.
منابع مشابه
Non-functional Requirements in Software Architecture Practice
Dealing with non-functional requirements (NFRs) has posed a challenge onto software engineers for many years. Over the years, many methods and techniques have been proposed to improve their elicitation, documentation, and validation. Knowing more about the state of the practice on these topics may benefit both practitioners’ and researchers’ daily work. A few empirical studies have been conduct...
متن کاملHow Do Software Architects Specify and Validate Quality Requirements?
Software architecture is the result of a design effort aimed at ensuring a certain set of quality attributes. As we show, quality requirements are commonly specified in practice but are rarely validated using automated techniques. In this paper we analyze and classify commonly specified quality requirements after interviewing professionals and running a survey. We report on tools used to valida...
متن کاملHow Architects See Non-Functional Requirements: Beware of Modifiability
This paper presents the analysis and key findings of a survey about dealing with non-functional requirements (NFRs) among architects. We find that, as long as the architect is aware of the importance of NFRs, they do not adversely affect project success, with one exception: highly business critical modifiability tends to be detrimental to project success, even when the architect is aware of it....
متن کاملHow Architects See Non-Functional Requirements: Beware of Modifiability
This chapter presents the analysis and key findings of a survey about dealing with nonfunctional requirements (NFRs) among architects. We find that, as long as the architect is aware of the importance of NFRs, they do not adversely affect project success, with one exception: highly business critical modifiability tends to be detrimental to project success, even when the architect is aware of it...
متن کاملExperiences from the Architectural Change Process
A good software architecture is becoming recognized as a major factor for successful products. There has been much research on the technical aspects of software architecture and it is recognized that the driving requirements for architectures are "non-functional", but few have studied how organizations decide on architectural changes. In this paper we study the topic through several case studie...
متن کامل